Method and apparatus for selecting sidelink resource in nr v2x

ABSTRACT

Provided are a method in which a first device ( 100 ) determines whether information related to a sidelink resource is valid, and an apparatus supporting same. The method comprises the steps of: receiving information related to a sidelink resource from a second apparatus ( 200 ); and determining whether the information related to the sidelink resource is valid, on the basis of the power of a signal received from the second device ( 200 ).

BACKGROUND OF THE DISCLOSURE Field of the Disclosure

The present disclosure relates to a wireless communication system.

Related Art

A wireless communication system is a multiple access system that supports communication of multiple users by sharing available system resources (e.g. a bandwidth, transmission power, etc.) among them. Examples of multiple access systems include a Code Division Multiple Access (CDMA) system, a Frequency Division Multiple Access (FDMA) system, a Time Division Multiple Access (TDMA) system, an Orthogonal Frequency Division Multiple Access (OFDMA) system, a Single Carrier Frequency Division Multiple Access (SC-FDMA) system, and a Multi-Carrier Frequency Division Multiple Access (MC-FDMA) system.

Meanwhile, a wireless communication system needs to estimate an uplink channel or downlink channel for data transmission/reception, system synchronization acquisition, channel information feedback, and so on. In a wireless communication system environment, fading occurs due to multi path time latency. A process of recovering a transmission signal by compensating distortion in a signal, which is caused by an abrupt environment change due to fading, is referred to as channel estimation. Additionally, a channel state for a cell to which the UE belongs or another cell needs to be measured. For channel estimation or channel state measurement, channel estimation is generally performed by using a reference signal (RS), which is mutually known between transceivers.

A UE may perform measurement using the following three methods.

1) Reference signal received power (RSRP): RSRP indicates the average received power of all resource elements (REs) carrying CRSs transmitted over the entire band. Here, the UE may measure the average received power of all REs carrying channel state information (CSI) RSs instead of CRSs.

2) Received signal strength indicator (RSSI): RSSI indicates received power measured over the entire band. RSSI includes all of a signal, interference, and thermal noise.

3) Reference symbol received quality (RSRQ): RSRQ indicates a channel quality indicator (CQI) and may be determined as RSRP/RSSI depending on a bandwidth or a sub-band. That is, RSRQ refers to signal-to-interference-plus-noise-ratio (SINR). Since RSRP does not provide sufficient mobility information, RSRQ may be used instead of RSRP in a handover or cell reselection process.

RSRQ may be calculated by RSSI/RSSP. Alternatively, RSRQ may be calculated by N*RSSI/RSSP. Here, N may be a parameter (for example, the number of PRBs) or a function associated with a bandwidth in which RSSI is measured.

Meanwhile, sidelink (SL) communication is a communication scheme in which a direct link is established between User Equipments (UEs) and the UEs exchange voice and data directly with each other without intervention of an evolved Node B (eNB). SL communication is under consideration as a solution to the overhead of an eNB caused by rapidly increasing data traffic.

Vehicle-to-everything (V2X) refers to a communication technology through which a vehicle exchanges information with another vehicle, a pedestrian, an object having an infrastructure (or infra) established therein, and so on. The V2X may be divided into 4 types, such as vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and vehicle-to-pedestrian (V2P). The V2X communication may be provided via a PC5 interface and/or Uu interface.

Meanwhile, as a wider range of communication devices require larger communication capacities, the need for mobile broadband communication that is more enhanced than the existing Radio Access Technology (RAT) is rising. Accordingly, discussions are made on services and user equipment (UE) that are sensitive to reliability and latency. And, a next generation radio access technology that is based on the enhanced mobile broadband communication, massive MTC, Ultra-Reliable and Low Latency Communication (URLLC), and so on, may be referred to as a new radio access technology (RAT) or new radio (NR). Herein, the NR may also support vehicle-to-everything (V2X) communication.

SUMMARY OF THE DISCLOSURE Technical Objects

Meanwhile, in SL communication, it is necessary for a UE to select resource(s) for SL transmission efficiently. For example, in case the UE selects resource(s) for SL transmission by itself, it is necessary for the UE to efficiently select resource(s) for SL transmission so as to minimize interference with other UEs.

Technical Solutions

In an embodiment, a method for determining, by a first device (100), whether or not information related to a sidelink (SL) resource is valid is provided. The method may comprise: receiving the information related to the SL resource from a second device (200); and determining whether or not the information related to the SL resource is valid, based on power of a signal received from the second device (200).

In another embodiment, a first device (100) determining whether or not information related to a sidelink (SL) resource is valid is provided. The first device (100) may comprise: one or more memories; one or more transceivers; and one or more processors connected to the one or more memories and the one or more transceivers. The one or more processors may be configured to: receive the information related to the SL resource from a second device (200); and determine whether or not the information related to the SL resource is valid, based on power of a signal received from the second device (200).

Effects of the Disclosure

A UE can perform SL communication efficiently.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a structure of an LTE system, in accordance with an embodiment of the present disclosure.

FIG. 2 shows a radio protocol architecture of a user plane, in accordance with an embodiment of the present disclosure.

FIG. 3 shows a radio protocol architecture of a control plane, in accordance with an embodiment of the present disclosure.

FIG. 4 shows a structure of an NR system, in accordance with an embodiment of the present disclosure.

FIG. 5 shows a functional division between an NG-RAN and a 5GC, in accordance with an embodiment of the present disclosure.

FIG. 6 shows a structure of a radio frame of an NR, in accordance with an embodiment of the present disclosure.

FIG. 7 shows a structure of a slot of an NR frame, in accordance with an embodiment of the present disclosure.

FIG. 8 shows an example of a BWP, in accordance with an embodiment of the present disclosure.

FIG. 9 shows a protocol stack for a SL communication, in accordance with an embodiment of the present disclosure.

FIG. 10 shows a protocol stack for a SL communication, in accordance with an embodiment of the present disclosure.

FIG. 11 shows a UE performing V2X or SL communication, in accordance with an embodiment of the present disclosure.

FIG. 12 shows a resource unit for V2X or SL communication, in accordance with an embodiment of the present disclosure.

FIG. 13 shows procedures of a UE performing V2X or SL communication according to a transmission mode (TM), in accordance with an embodiment of the present disclosure.

FIG. 14 shows a method of selecting a transmission resource by a UE, in accordance with an embodiment of the present disclosure.

FIG. 15 shows a synchronization source or synchronization reference of V2X, in accordance with an embodiment of the present disclosure.

FIG. 16 shows a method for measuring, by a UE, a channel busy ratio (CBR), in accordance with an embodiment of the present disclosure.

FIG. 17 shows three different cast types, in accordance with an embodiment of the present disclosure.

FIG. 18 shows a procedure for a UE to determine validity of information related to SL resource(s), in accordance with an embodiment of the present disclosure.

FIG. 19 shows a method for determining, by a first device (100), whether or not information related to a sidelink (SL) resource is valid, in accordance with an embodiment of the present disclosure.

FIG. 20 shows a communication system 1, in accordance with an embodiment of the present disclosure.

FIG. 21 shows wireless devices, in accordance with an embodiment of the present disclosure.

FIG. 22 shows a signal process circuit for a transmission signal, in accordance with an embodiment of the present disclosure.

FIG. 23 shows another example of a wireless device, in accordance with an embodiment of the present disclosure.

FIG. 24 shows a hand-held device, in accordance with an embodiment of the present disclosure.

FIG. 25 shows a vehicle or an autonomous vehicle, in accordance with an embodiment of the present disclosure.

FIG. 26 shows a vehicle, in accordance with an embodiment of the present disclosure.

FIG. 27 shows an XR device, in accordance with an embodiment of the present disclosure.

FIG. 28 shows a robot, in accordance with an embodiment of the present disclosure.

FIG. 29 shows an AI device, in accordance with an embodiment of the present disclosure.

DESCRIPTION OF EXEMPLARY EMBODIMENTS

In various embodiments of the present disclosure, it shall be interpreted that “I” and “,” indicate “and/or”. For example, “A/B” may mean “A and/or B”. Additionally, “A, B” may also mean “A and/or B”. Moreover, “A/B/C” may mean “at least one of A, B and/or C”. Furthermore, “A, B, C” may also mean “at least one of A, B and/or C”.

Furthermore, in various embodiments of the present disclosure, it shall be interpreted that “or” indicates “and/or”. For example, “A or B” may include “only A”, “only B”, and/or “both A and B”. In other words, in various embodiments of the present disclosure, it shall be interpreted that “or” indicates “additionally or alternatively”.

The technology described below may be used in various wireless communication systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and so on. The CDMA may be implemented with a radio technology, such as universal terrestrial radio access (UTRA) or CDMA-2000. The TDMA may be implemented with a radio technology, such as global system for mobile communications (GSM)/general packet ratio service (GPRS)/enhanced data rate for GSM evolution (EDGE). The OFDMA may be implemented with a radio technology, such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, evolved UTRA (E-UTRA), and so on. IEEE 802.16m is an evolved version of IEEE 802.16e and provides backward compatibility with a system based on the IEEE 802.16e. The UTRA is part of a universal mobile telecommunication system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is part of an evolved UMTS (E-UMTS) using the E-UTRA. The 3GPP LTE uses the OFDMA in a downlink and uses the SC-FDMA in an uplink. LTE-advanced (LTE-A) is an evolution of the LTE.

5G NR is a successive technology of LTE-A corresponding to a new Clean-slate type mobile communication system having the characteristics of high performance, low latency, high availability, and so on. 5G NR may use resources of all spectrum available for usage including low frequency bands of less than 1 GHz, middle frequency bands ranging from 1 GHz to 10 GHz, high frequency (millimeter waves) of 24 GHz or more, and so on.

For clarity in the description, the following description will mostly focus on LTE-A or 5G NR. However, technical features of the present disclosure will not be limited only to this.

FIG. 1 shows a structure of an LTE system, in accordance with an embodiment of the present disclosure. This may also be referred to as an Evolved-UMTS Terrestrial Radio Access Network (E-UTRAN), or a Long Term Evolution (LTE)/LTE-A system.

Referring to FIG. 1, the E-UTRAN includes a base station (BS) 20, which provides a control plane and a user plane to a user equipment (UE) 10. The UE 10 may be fixed or mobile and may also be referred to by using different terms, such as Mobile Station (MS), User Terminal (UT), Subscriber Station (SS), Mobile Terminal (MT), wireless device, and so on. The base station 20 refers to a fixed station that communicates with the UE 10 and may also be referred to by using different terms, such as evolved-NodeB (eNB), Base Transceiver System (BTS), Access Point (AP), and so on.

The base stations 20 are interconnected to one another through an X2 interface. The base stations 20 are connected to an Evolved Packet Core (EPC) 30 through an S1 interface. More specifically, the base station 20 are connected to a Mobility Management Entity (MME) through an S1-MME interface and connected to Serving Gateway (S-GW) through an S1-U interface.

The EPC 30 is configured of an MME, an S-GW, and a Packet Data Network-Gateway (P-GW). The MME has UE access information or UE capability information, and such information may be primarily used in UE mobility management. The S-GW corresponds to a gateway having an E-UTRAN as its endpoint. And, the P-GW corresponds to a gateway having a Packet Data Network (PDN) as its endpoint.

Layers of a radio interface protocol between the UE and the network may be classified into a first layer (L1), a second layer (L2), and a third layer (L3) based on the lower three layers of an open system interconnection (OSI) model, which is well-known in the communication system. Herein, a physical layer belonging to the first layer provides a physical channel using an Information Transfer Service, and a Radio Resource Control (RRC) layer, which is located in the third layer, executes a function of controlling radio resources between the UE and the network. For this, the RRC layer exchanges RRC messages between the UE and the base station.

FIG. 2 shows a radio protocol architecture of a user plane, in accordance with an embodiment of the present disclosure. FIG. 3 shows a radio protocol architecture of a control plane, in accordance with an embodiment of the present disclosure. The user plane is a protocol stack for user data transmission, and the control plane is a protocol stack for control signal transmission.

Referring to FIG. 2 and FIG. 3, a physical (PHY) layer belongs to the L1. A physical (PHY) layer provides an information transfer service to a higher layer through a physical channel. The PHY layer is connected to a medium access control (MAC) layer. Data is transferred (or transported) between the MAC layer and the PHY layer through a transport channel. The transport channel is sorted (or categorized) depending upon how and according to which characteristics data is being transferred through the radio interface.

Between different PHY layers, i.e., a PHY layer of a transmitter and a PHY layer of a receiver, data is transferred through the physical channel. The physical channel may be modulated by using an orthogonal frequency division multiplexing (OFDM) scheme and uses time and frequency as radio resource.

The MAC layer provides services to a radio link control (RLC) layer, which is a higher layer of the MAC layer, via a logical channel. The MAC layer provides a function of mapping multiple logical channels to multiple transport channels. The MAC layer also provides a function of logical channel multiplexing by mapping multiple logical channels to a single transport channel. The MAC layer provides data transfer services over logical channels.

The RLC layer performs concatenation, segmentation, and reassembly of Radio Link Control Service Data Unit (RLC SDU). In order to ensure various quality of service (QoS) required by a radio bearer (RB), the RLC layer provides three types of operation modes, i.e., a transparent mode (TM), an unacknowledged mode (UM), and an acknowledged mode (AM). An AM RLC provides error correction through an automatic repeat request (ARQ).

The radio resource control (RRC) layer is defined only in a control plane. And, the RRC layer performs a function of controlling logical channel, transport channels, and physical channels in relation with configuration, re-configuration, and release of radio bearers. The RB refers to a logical path being provided by the first layer (PHY layer) and the second layer (MAC layer, RLC layer, Packet Data Convergence Protocol (PDCP) layer) in order to transport data between the UE and the network.

Functions of a PDCP layer in the user plane include transfer, header compression, and ciphering of user data. Functions of a PDCP layer in the control plane include transfer and ciphering/integrity protection of control plane data.

The configuration of the RB refers to a process for specifying a radio protocol layer and channel properties in order to provide a particular service and for determining respective detailed parameters and operation methods. The RB may then be classified into two types, i.e., a signaling radio bearer (SRB) and a data radio bearer (DRB). The SRB is used as a path for transmitting an RRC message in the control plane, and the DRB is used as a path for transmitting user data in the user plane.

When an RRC connection is established between an RRC layer of the UE and an RRC layer of the E-UTRAN, the UE is in an RRC_CONNECTED state, and, otherwise, the UE may be in an RRC_IDLE state. In case of the NR, an RRC_INACTIVE state is additionally defined, and a UE being in the RRC_INACTIVE state may maintain its connection with a core network whereas its connection with the base station is released.

Downlink transport channels transmitting (or transporting) data from a network to a UE include a Broadcast Channel (BCH) transmitting system information and a downlink Shared Channel (SCH) transmitting other user traffic or control messages. Traffic or control messages of downlink multicast or broadcast services may be transmitted via the downlink SCH or may be transmitted via a separate downlink Multicast Channel (MCH). Meanwhile, uplink transport channels transmitting (or transporting) data from a UE to a network include a Random Access Channel (RACH) transmitting initial control messages and an uplink Shared Channel (SCH) transmitting other user traffic or control messages.

Logical channels existing at a higher level than the transmission channel and being mapped to the transmission channel may include a Broadcast Control Channel (BCCH), a Paging Control Channel (PCCH), a Common Control Channel (CCCH), a Multicast Control Channel (MCCH), a Multicast Traffic Channel (MTCH), and so on.

A physical channel is configured of a plurality of OFDM symbols in the time domain and a plurality of sub-carriers in the frequency domain. One subframe is configured of a plurality of OFDM symbols in the time domain. A resource block is configured of a plurality of OFDM symbols and a plurality of sub-carriers in resource allocation units. Additionally, each subframe may use specific sub-carriers of specific OFDM symbols (e.g., first OFDM symbol) of the corresponding subframe for a Physical Downlink Control Channel (PDCCH), i.e., L1/L2 control channels. A Transmission Time Interval (TTI) refers to a unit time of a subframe transmission.

FIG. 4 shows a structure of an NR system, in accordance with an embodiment of the present disclosure.

Referring to FIG. 4, a Next Generation—Radio Access Network (NG-RAN) may include a next generation-Node B (gNB) and/or eNB providing a user plane and control plane protocol termination to a user. FIG. 4 shows a case where the NG-RAN includes only the gNB. The gNB and the eNB are connected to one another via Xn interface. The gNB and the eNB are connected to one another via 5^(th) Generation (5G) Core Network (5GC) and NG interface. More specifically, the gNB and the eNB are connected to an access and mobility management function (AMF) via NG-C interface, and the gNB and the eNB are connected to a user plane function (UPF) via NG-U interface.

FIG. 5 shows a functional division between an NG-RAN and a 5GC, in accordance with an embodiment of the present disclosure.

Referring to FIG. 5, the gNB may provide functions, such as Inter Cell Radio Resource Management (RRM), Radio Bearer (RB) control, Connection Mobility Control, Radio Admission Control, Measurement Configuration & Provision, Dynamic Resource Allocation, and so on. An AMF may provide functions, such as Non Access Stratum (NAS) security, idle state mobility processing, and so on. A UPF may provide functions, such as Mobility Anchoring, Protocol Data Unit (PDU) processing, and so on. A Session Management Function (SMF) may provide functions, such as user equipment (UE) Internet Protocol (IP) address allocation, PDU session control, and so on.

FIG. 6 shows a structure of a radio frame of an NR, in accordance with an embodiment of the present disclosure.

Referring to FIG. 6, in the NR, a radio frame may be used for performing uplink and downlink transmission. A radio frame has a length of 10 ms and may be defined to be configured of two half-frames (HFs). A half-frame may include five 1 ms subframes (SFs). A subframe (SF) may be divided into one or more slots, and the number of slots within a subframe may be determined in accordance with subcarrier spacing (SCS). Each slot may include 12 or 14 OFDM(A) symbols according to a cyclic prefix (CP).

In case of using a normal CP, each slot may include 14 symbols. In case of using an extended CP, each slot may include 12 symbols. Herein, a symbol may include an OFDM symbol (or CP-OFDM symbol) and a Single Carrier-FDMA (SC-FDMA) symbol (or Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) symbol).

Table 1 shown below represents an example of a number of symbols per slot (N^(slot) _(symb)), a number slots per frame (N^(frame,μ) _(slot)), and a number of slots per subframe (N^(subframe,μ) _(slot)) in accordance with an SCS configuration (u), in a case where a normal CP is used.

TABLE 1 SCS (15*2^(u)) N^(slot) _(symb) N^(frame,u) _(slot) N^(subframe,u) _(slot)  15 KHz (u = 0) 14 10 1  30 KHz (u = 1) 14 20 2  60 KHz (u = 2) 14 40 4 120 KHz (u = 3) 14 80 8 240 KHz (u = 4) 14 160 16

Table 2 shows an example of a number of symbols per slot, a number of slots per frame, and a number of slots per subframe in accordance with the SCS, in a case where an extended CP is used.

TABLE 2 SCS (15 *2U) N^(slot) _(symb) N^(frame,u) _(slot) N^(subframe,u) _(slot) 60 KHz (u = 2) 12 40 4

In an NR system, OFDM(A) numerologies (e.g., SCS, CP length, and so on) between multiple cells being integrate to one UE may be differently configured. Accordingly, a (absolute time) duration (or section) of a time resource (e.g., subframe, slot or TTI) (collectively referred to as a time unit (TU) for simplicity) being configured of the same number of symbols may be differently configured in the integrated cells.

In the NR, multiple numerologies or SCSs for supporting various 5G services may be supported. For example, in case an SCS is 15 kHz, a wide area of the conventional cellular bands may be supported, and, in case an SCS is 30 kHz/60 kHz a dense-urban, lower latency, wider carrier bandwidth may be supported. In case the SCS is 60 kHz or higher, a bandwidth that is greater than 24.25 GHz may be used in order to overcome phase noise.

An NR frequency band may be defined as two different types of frequency ranges. The two different types of frequency ranges may be FR1 and FR2. The values of the frequency ranges may be changed (or varied), and, for example, the two different types of frequency ranges may be as shown below in Table 3. Among the frequency ranges that are used in an NR system, FR1 may mean a “sub 6 GHz range”, and FR2 may mean an “above 6 GHz range” and may also be referred to as a millimeter wave (mmW).

TABLE 3 Frequency Range Corresponding Subcarrier designation frequency range Spacing (SCS) FR1 450 MHz-6000 MHz 15, 30, 60 kHz FR2 24250 MHz-52600 MHz 60, 120, 240 kHz

As described above, the values of the frequency ranges in the NR system may be changed (or varied). For example, as shown below in Table 4, FR1 may include a band within a range of 410 MHz to 7125 MHz. More specifically, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, and so on) and higher. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, and so on) and higher being included in FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, e.g., the unlicensed band for vehicle-specific communication (e.g., autonomous driving).

TABLE 4 Frequency Range Corresponding Subcarrier designation frequency range Spacing (SCS) FR1 410 MHz-7125 MHz 15, 30, 60 kHz FR2 24250 MHz-52600 MHz 60, 120, 240 kHz

FIG. 7 shows a structure of a slot of an NR frame, in accordance with an embodiment of the present disclosure.

Referring to FIG. 7, a slot includes a plurality of symbols in a time domain. For example, in case of a normal CP, one slot may include 14 symbols. However, in case of an extended CP, one slot may include 12 symbols. Alternatively, in case of a normal CP, one slot may include 7 symbols. However, in case of an extended CP, one slot may include 6 symbols.

A carrier includes a plurality of subcarriers in a frequency domain. A Resource Block (RB) may be defined as a plurality of consecutive subcarriers (e.g., 12 subcarriers) in the frequency domain. A Bandwidth Part (BWP) may be defined as a plurality of consecutive (Physical) Resource Blocks ((P)RBs) in the frequency domain, and the BWP may correspond to one numerology (e.g., SCS, CP length, and so on). A carrier may include a maximum of N number BWPs (e.g., 5 BWPs). Data communication may be performed via an activated BWP. Each element may be referred to as a Resource Element (RE) within a resource grid and one complex symbol may be mapped to each element.

Hereinafter, a Bandwidth Part (BWP) and a carrier will be described in detail.

The Bandwidth Part (BWP) may be a continuous set of physical resource blocks (PRBs) within a given numerology. The PRB may be selected from a continuous partial set of a common resource block (CRB) for a given numerology on a given carrier.

When using Bandwidth Adaptation (BA), a receiving bandwidth and a transmitting bandwidth of a user equipment (UE) are not required to be as wide (or large) as the bandwidth of the cell, and the receiving bandwidth and the transmitting bandwidth of the UE may be controlled (or adjusted). For example, the UE may receive information/configuration for bandwidth control (or adjustment) from a network/base station. In this case, the bandwidth control (or adjustment) may be performed based on the received information/configuration. For example, the bandwidth control (or adjustment) may include reduction/expansion of the bandwidth, position change of the bandwidth, or change in subcarrier spacing of the bandwidth.

For example, the bandwidth may be reduced during a duration with little activity in order to save power. For example, a position of the bandwidth may be relocated (or moved) from a frequency domain. For example, the position of the bandwidth may be relocated (or moved) from a frequency domain in order to enhance scheduling flexibility. For example, subcarrier spacing of the bandwidth may be changed. For example, the subcarrier spacing of the bandwidth may be changed in order to authorize different services. A subset of a total cell bandwidth of a cell may be referred to as a Bandwidth Part (BWP). BA may be performed when a base station/network configures BWPs to the UE, and when the base station/network notifies the BWP that is currently in an active state, among the BWPs, to the UE.

For example, the BWP may be one of an active BWP, an initial BWP, and/or a default BWP. For example, the UE may not monitor a downlink radio link quality in a DL BWP other than the active DL BWP within a primary cell (PCell). For example, the UE may not receive a PDCCH, a PDSCH or a CSI-RS (excluding only the RRM) from outside of the active DL BWP. For example, the UE may not trigger a Channel State Information (CSI) report for an inactive DL BWP. For example, the UE may not transmit a PUCCH or a PUSCH from outside of an inactive DL BWP. For example, in case of a downlink, an initial BWP may be given as a continuous RB set for an RMSI CORESET (that is configured by a PBCH). For example, in case of an uplink, an initial BWP may be given by a SIB for a random access procedure. For example, a default BWP may be configured by a higher layer. For example, an initial value of a default BWP may be an initial DL BWP. For energy saving, if the UE fails to detect DCI during a predetermined period of time, the UE may switch the active BWP of the UE to a default BWP.

Meanwhile, a BWP may be defined for the SL. The same SL BWP may be used for transmission and reception. For example, a transmitting UE may transmit an SL channel or SL signal within a specific BWP, and a receiving UE may receive an SL channel or SL signal within the same specific BWP. In a licensed carrier, the SL BWP may be defined separately from a Uu BWP, and the SL BWP may have a separate configuration signaling from the Uu BWP. For example, the UE may receive a configuration for an SL BWP from the base station/network. The SL BWP may be configured (in advance) for an out-of-coverage NR V2X UE and an RRC_IDLE UE. For a UE operating in the RRC_CONNECTED mode, at least one SL BWP may be activated within a carrier.

FIG. 8 shows an example of a BWP, in accordance with an embodiment of the present disclosure. In the embodiment of FIG. 8, it is assumed that three BWPs exist.

Referring to FIG. 8, a common resource block (CRB) may be a carrier resource block that is numerated from one end of a carrier band to another end. And, a PRB may be a resource block that is numerated within each BWP. Point A may indicate a common reference point for a resource block grid.

A BWP may be configured by Point A, an offset (N^(start) _(BWP)) from Point A, and a bandwidth (N^(size) _(BWP)). For example, Point A may be an external reference point of a PRB of a carrier having subcarrier 0 of all numerologies (e.g., all numerologies being supported by the network within the corresponding carrier) aligned therein. For example, the offset may be a PRB distance between a lowest subcarrier within a given numerology and Point A. For example, the bandwidth may be a number of PRBs within the given numerology.

Hereinafter, V2X or SL communication will be described.

FIG. 9 shows a protocol stack for a SL communication, in accordance with an embodiment of the present disclosure. More specifically, (a) of FIG. 9 shows a user plane protocol stack of LTE, and (b) of FIG. 9 shows a control plane protocol stack of LTE.

FIG. 10 shows a protocol stack for a SL communication, in accordance with an embodiment of the present disclosure. More specifically, (a) of FIG. 10 shows a user plane protocol stack of NR, and (b) of FIG. 10 shows a control plane protocol stack of NR.

Hereinafter, SL Synchronization Signal (SLSS) and synchronization information will be described.

SLSS is a SL specific sequence, which may include a Primary Sidelink Synchronization Signal (PSSS) and a Secondary Sidelink Synchronization Signal (SSSS). The PSSS may also be referred to as a Sidelink Primary Synchronization Signal (S-PSS), and the SSSS may also be referred to as a Sidelink Secondary Synchronization Signal (S-SSS).

A Physical Sidelink Broadcast Channel (PSBCH) may be a (broadcast) channel through which basic (system) information that should first be known by the user equipment (UE) before transmitting and receiving SL signals. For example, the basic information may be information related to SLSS, a Duplex mode (DM), Time Division Duplex Uplink/Downlink (TDD UL/DL) configuration, information related to a resource pool, application types related to SLSS, a subframe offset, broadcast information, and so on.

The S-PSS, the S-SSS, and the PSBCH may be included in a block format (e.g., a SL SS/PSBCH block, hereinafter referred to as Sidelink-Synchronization Signal Block (S-SSB)). The S-SSB may have the same numerology (i.e., SCS and CP length) as a Physical Sidelink Control Channel (PSCCH)/Physical Sidelink Shared Channel (PSSCH) within the carrier, and a transmission bandwidth may exist within a (pre-)configured SL Bandwidth Part (BWP). And, a frequency position of the S-SSB may be (pre-)configured. Therefore, the UE is not required to perform a hypothesis detection in order to discover the S-SSB in the carrier.

Each SLSS may have a physical layer SL synchronization identity (ID), and the respective value may be equal to any one value ranging from 0 to 335. Depending upon one of the above-described values that is used, a synchronization source may also be identified. For example, values of 0, 168, 169 may indicate global navigation satellite systems (GNSS), values from 1 to 167 may indicate base stations, and values from 170 to 335 may indicate that the source is outside of the coverage. Alternatively, among the physical layer SL synchronization ID values, values 0 to 167 may correspond to value being used by a network, and values from 168 to 335 may correspond to value being used outside of the network coverage.

FIG. 11 shows a UE performing V2X or SL communication, in accordance with an embodiment of the present disclosure.

Referring to FIG. 11, in V2X/SL communication, the term terminal may mainly refer to a terminal (or equipment) used by a user. However, in case a network equipment, such as a base station, transmits and receives signals in accordance with a communication scheme between the network equipment and a user equipment (UE) (or terminal), the base station may also be viewed as a type of user equipment (or terminal).

User equipment 1 (UE1) may select a resource unit corresponding to a specific resource within a resource pool, which refers to a set of resources, and UE1 may then be operated so as to transmit a SL signal by using the corresponding resource unit. User equipment 2 (UE2), which is to a receiving UE, may be configured with a resource pool to which UE1 can transmit signals, and may then detect signals of UE1 from the corresponding resource pool.

Herein, in case UE1 is within a connection range of the base station, the base station may notify the resource pool. Conversely, in case UE1 is outside a connection range of the base station, another UE may notify the resource pool or a pre-determined resource may be used.

Generally, a resource pool may be configured in a plurality of resource units, and each UE may select one resource unit or a plurality of resource units and may use the selected resource unit(s) for its SL signal transmission.

FIG. 12 shows a resource unit for V2X or SL communication, in accordance with an embodiment of the present disclosure.

Referring to FIG. 12, the total frequency resources of the resource pool may be divided into NF number of resource units, the total time resources of the resource pool may be divided into NT number of resource units. Therefore, a total of NF*NT number of resource units may be defined in the resource pool. FIG. 12 shows an example of a case where the corresponding resource pool is repeated at a cycle of NT number of subframes.

As shown in FIG. 12, one resource unit (e.g., Unit #0) may be periodically and repeatedly indicated. Alternatively, in order to achieve a diversity effect in the time or frequency level (or dimension), an index of a physical resource unit to which a logical resource unit is mapped may be changed to a pre-determined pattern in accordance with time. In such resource unit structure, the resource pool may refer to a set of resource units that can be used for a transmission that is performed by a user equipment (UE), which intends to transmit SL signals.

The resource pool may be segmented to multiple types. For example, depending upon the content of a SL signal being transmitted from each resource pool, the resource pool may be divided as described below.

(1) Scheduling Assignment (SA) may correspond to a signal including information, such as a position of a resource that is used for the transmission of a SL data channel, a Modulation and Coding Scheme (MCS) or Multiple Input Multiple Output (MIMO) transmission scheme needed for the modulation of other data channels, a Timing Advance (TA), and so on. The SA may also be multiplexed with SL data within the same resource unit and may then be transmitted, and, in this case, an SA resource pool may refer to a resource pool in which the SA is multiplexed with the SL data and then transmitted. The SA may also be referred to as a SL control channel.

(2) A Physical Sidelink Shared Channel (PSSCH) may be a resource pool that is used by a transmitting UE for transmitting user data. If the SA is multiplexed with SL data within the same resource unit and then transmitted, only a SL data channel excluding the SA information may be transmitted from the resource pool that is configured for the SL data channel. In other words, REs that were used for transmitting SA information within a separate resource unit of the SA resource pool may still be used for transmitting SL data from the resource pool of a SL data channel.

(3) A discovery channel may be a resource pool that is used by the transmitting UE for transmitting information, such as its own ID. By doing so, the transmitting UE may allow a neighboring UE to discover the transmitting UE.

Even if the content of the above-described SL signal is the same, different resource pools may be used depending upon the transmission/reception attribute of the SL signal. For example, even if the same SL data channel or discovery message is used, the resource pool may be identified as a different resource pool depending upon a transmission timing decision method (e.g., whether the transmission is performed at a reception point of the synchronization reference signal or whether transmission is performed at the reception point by applying a consistent timing advance), a resource allocation method (e.g., whether the base station designates a transmission resource of a separate signal to a separate transmitting UE or whether a separate transmitting UE selects a separate signal transmission resource on its own from the resource pool), and a signal format (e.g., a number of symbols occupied by each SL signal within a subframe or a number of subframes being used for the transmission of one SL signal) of the SL signal, signal intensity from the base station, a transmitting power intensity (or level) of a SL UE, and so on.

Hereinafter, resource allocation in a SL will be described.

FIG. 13 shows procedures of a UE performing V2X or SL communication according to a transmission mode (TM), in accordance with an embodiment of the present disclosure. Specifically, (a) of FIG. 13 shows a UE operation related to a transmission mode 1 or a transmission mode 3, and (b) of FIG. 13 shows a UE operation related to a transmission mode 2 or a transmission mode 4.

Referring to (a) of FIG. 13, in transmission modes 1/3, the base station performs resource scheduling to UE1 via PDCCH (more specifically, Downlink Control Information (DCI)), and UE1 performs SL/V2X communication with UE2 according to the corresponding resource scheduling. After transmitting sidelink control information (SCI) to UE2 via physical sidelink control channel (PSCCH), UE1 may transmit data based on the SCI via physical sidelink shared channel (PSSCH). In case of an LTE SL, transmission mode 1 may be applied to a general SL communication, and transmission mode 3 may be applied to a V2X SL communication.

Referring to (b) of FIG. 13, in transmission modes 2/4, the UE may schedule resources on its own. More specifically, in case of LTE SL, transmission mode 2 may be applied to a general SL communication, and the UE may select a resource from a predetermined resource pool on its own and may then perform SL operations. Transmission mode 4 may be applied to a V2X SL communication, and the UE may carry out a sensing/SA decoding procedure, and so on, and select a resource within a selection window on its own and may then perform V2X SL operations. After transmitting the SCI to UE2 via PSCCH, UE1 may transmit SCI-based data via PSSCH. Hereinafter, the transmission mode may be abbreviated to the term mode.

In case of NR SL, at least two types of SL resource allocation modes may be defined. In case of mode 1, the base station may schedule SL resources that are to be used for SL transmission. In case of mode 2, the user equipment (UE) may determine a SL transmission resource from SL resources that are configured by the base station/network or predetermined SL resources. The configured SL resources or the pre-determined SL resources may be a resource pool. For example, in case of mode 2, the UE may autonomously select a SL resource for transmission. For example, in case of mode 2, the UE may assist (or help) SL resource selection of another UE. For example, in case of mode 2, the UE may be configured with an NR configured grant for SL transmission. For example, in case of mode 2, the UE may schedule SL transmission of another UE. And, mode 2 may at least support reservation of SL resources for blind retransmission.

Procedures related to sensing and resource (re-)selection may be supported in resource allocation mode 2. The sensing procedure may be defined as a process decoding the SCI from another UE and/or SL measurement. The decoding of the SCI in the sensing procedure may at least provide information on a SL resource that is being indicated by a UE transmitting the SCI. When the corresponding SCI is decoded, the sensing procedure may use L1 SL Reference Signal Received Power (RSRP) measurement, which is based on SL Demodulation Reference Signal (DMRS). The resource (re-)selection procedure may use a result of the sensing procedure in order to determine the resource for the SL transmission.

FIG. 14 shows a method of selecting a transmission resource by a UE, in accordance with an embodiment of the present disclosure.

Referring to FIG. 14, the UE may identify transmission resources reserved by another UE or resources being used by another UE via sensing within a sensing window, and, after excluding the identified resources from a selection window, the UE may randomly select a resource from resources having low interference among the remaining resources.

For example, within the sensing window, the UE may decode the PSCCH including information on the cycles of the reserved resources, and, then, the UE may measure a PSSCH RSRP from resources that are periodically determined based on the PSCCH. The UE may exclude resources having the PSSCH RSRP that exceeds a threshold value from the selection window. Thereafter, the UE may randomly select a SL resource from the remaining resources within the selection window.

Alternatively, the UE may measure a Received Signal Strength Indicator (RSSI) of the periodic resources within the sensing window and may then determine the resources having low interference (e.g., the lower 20% of the resources). Additionally, the UE may also randomly select a SL resource from the resources included in the selection window among the periodic resources. For example, in case the UE fails to perform decoding of the PSCCH, the UE may use the above described methods.

Hereinafter, synchronization acquisition of an SL UE will be described.

In time division multiple access (TDMA) and frequency division multiple access (FDMA) systems, accurate time and frequency synchronization is essential. If the time and frequency synchronization is not accurate, system performance may be degraded due to inter symbol interference (ISI) and inter carrier interference (ICI). The same is true for V2X. In V2X, for time/frequency synchronization, sidelink synchronization signal (SLSS) may be used in a physical layer, and master information block-sidelink-V2X (MIB-SL-V2X) may be used in a radio link control (RLC) layer.

FIG. 15 shows a synchronization source or synchronization reference of V2X, in accordance with an embodiment of the present disclosure.

Referring to FIG. 15, in V2X, a UE may be directly synchronized with a global navigation satellite system (GNSS), or may be indirectly synchronized with the GNSS through a UE (inside network coverage or outside network coverage) directly synchronized with the GNSS. If the GNSS is configured as the synchronization source, the UE may calculate a DFN and a subframe number by using a coordinated universal time (UTC) and a (pre-)configured direct frame number (DFN) offset.

Alternatively, the UE may be directly synchronized with a BS, or may be synchronized with another UE which is time/frequency-synchronized with the BS. For example, the BS may be an eNB or a gNB. For example, if the UE is inside the network coverage, the UE may receive synchronization information provided by the BS, and may be directly synchronized with the BS. Thereafter, the UE may provide the synchronization information to adjacent another UE. If BS timing is configured based on synchronization, for synchronization and downlink measurement, the UE may be dependent on a cell related to a corresponding frequency (when it is inside the cell coverage at the frequency), or a primary cell or a serving cell (when it is outside the cell coverage at the frequency).

The BS (e.g., serving cell) may provide a synchronization configuration for a carrier used in V2X or SL communication. In this case, the UE may conform to the synchronization configuration received from the BS. If the UE fails to detect any cell in a carrier used in the V2X or SL communication and fails to receive the synchronization configuration from the serving cell, the UE may conform to a pre-configured synchronization configuration.

Alternatively, the UE may be synchronized with another UE which fails to obtain synchronization information directly or indirectly from the BS or the GNSS. A synchronization source or preference may be pre-configured to the UE. Alternatively, the synchronization source and preference may be configured through a control message provided by the BS.

An SL synchronization source may be associated/related with a synchronization priority. For example, a relation between the synchronization source and the synchronization priority may be defined as shown in Table 5. Table 5 is for exemplary purposes only, and the relation between the synchronization source and the synchronization priority may be defined in various forms.

TABLE 5 Priority eNB/gNB-based level GNSS-based synchronization synchronization P0 GNSS BS P1 All UEs directly synchronized All UEs directly synchronized with GNSS with BS P2 All UEs indirectly synchronized All UEs indirectly synchronized with GNSS with BS P3 All other UEs GNSS P4 N/A All UEs directly synchronized with GNSS P5 N/A All UEs indirectly synchronized with GNSS P6 N/A All other UEs

Whether to use GNSS-based synchronization or BS-based synchronization may be (pre-)configured. In a single-carrier operation, the UE may derive transmission timing of the UE from an available synchronization reference having the highest priority.

Hereinafter, sidelink (SL) congestion control will be described.

If a UE autonomously determines an SL transmission resource, the UE also autonomously determines a size and frequency of use for a resource used by the UE. Of course, due to a constraint from a network or the like, it may be restricted to use a resource size or frequency of use, which is greater than or equal to a specific level. However, if all UEs use a relatively great amount of resources in a situation where many UEs are concentrated in a specific region at a specific time, overall performance may significantly deteriorate due to mutual interference.

Accordingly, the UE may need to observe a channel situation. If it is determined that an excessively great amount of resources are consumed, it is preferable that the UE autonomously decreases the use of resources. In the present specification, this may be defined as congestion control (CR). For example, the UE may determine whether energy measured in a unit time/frequency resource is greater than or equal to a specific level, and may adjust an amount and frequency of use for its transmission resource based on a ratio of the unit time/frequency resource in which the energy greater than or equal to the specific level is observed. In the present specification, the ratio of the time/frequency resource in which the energy greater than or equal to the specific level is observed may be defined as a channel busy ratio (CBR). The UE may measure the CBR for a channel/frequency. Additionally, the UE may transmit the measured CBR to the network/BS.

FIG. 16 shows a method for measuring, by a UE, a channel busy ratio (CBR), in accordance with an embodiment of the present disclosure.

Referring to FIG. 16, CBR may denote the number of sub-channels in which a measurement result value of a received signal strength indicator (RSSI) has a value greater than or equal to a pre-configured threshold as a result of measuring the RSSI by a UE on a sub-channel basis for a specific period (e.g., 100 ms). Alternatively, the CBR may denote a ratio of sub-channels having a value greater than or equal to a pre-configured threshold among sub-channels for a specific duration. For example, in the embodiment of FIG. 16, if it is assumed that a hatched sub-channel is a sub-channel having a value greater than or equal to a pre-configured threshold, the CBR may denote a ratio of the hatched sub-channels for a period of 100 ms.

Further, congestion control considering a priority of traffic (e.g., packet) may be necessary. To this end, for example, the UE may measure a channel occupancy ratio (CR). Specifically, the UE may measure the CBR, and the UE may determine a maximum value CRlimitk of a channel occupancy ratio k (CRk) that can be occupied by traffic corresponding to each priority (e.g., k) based on the CBR. For example, the UE may derive the maximum value CRlimitk of the channel occupancy ratio with respect to a priority of each traffic, based on a predetermined table of CBR measurement values. For example, in case of traffic having a relatively high priority, the UE may derive a maximum value of a relatively great channel occupancy ratio. Thereafter, the UE may perform congestion control by restricting a total sum of channel occupancy ratios of traffic, of which a priority k is lower than i, to a value less than or equal to a specific value. Based on this method, the channel occupancy ratio may be more strictly restricted for traffic having a relatively low priority.

In addition thereto, the UE may perform SL congestion control by using a method of adjusting a level of transmit power, dropping a packet, determining whether retransmission is to be performed, adjusting a transmission RB size (MCS coordination), or the like.

FIG. 17 shows three different cast types, in accordance with an embodiment of the present disclosure.

More specifically, (a) of FIG. 17 shows a broadcast type SL communication, (b) of FIG. 17 shows a unicast type SL communication, and (c) of FIG. 17 shows a groupcast type SL communication. In case of the broadcast type SL communication, the UE may perform one-to-one communication with another UE. And, in case of the unicast type SL communication, the UE may perform SL communication with one or more other UEs within the group to which the corresponding UE belongs. In the various embodiments of the present disclosure, the SL groupcast communication may be replaced with SL multicast communication, SL one-to-many communication, and so on.

Meanwhile, in SL communication, it is necessary for the UE to select resource(s) for SL transmission efficiently. Hereinafter, according to various embodiments of the present disclosure, a method for selecting resource(s) for SL transmission efficiently by a UE and an apparatus supporting the same will be described. In various embodiments of the present disclosure, SL communication may include V2X communication.

At least one proposed method proposed according to various embodiments of the present disclosure may be applied to at least one of unicast communication, groupcast communication, and/or broadcast communication.

At least one proposed method proposed according to various embodiments of the present disclosure may be applied to not only SL communication or V2X communication based on PC5 interface or SL interface (e.g., PSCCH, PSSCH, PSBCH, PSSS/SSSS, etc.), but also SL communication or V2X communication based on Uu interface (e.g., PUSCH, PDSCH, PDCCH, PUCCH, etc.).

In various embodiments of the present disclosure, receiving operations of a UE may include decoding operations and/or receiving operations of a sidelink channel and/or sidelink signal (e.g., PSCCH, PSSCH, PSFCH, PSBCH, PSSS/SSSS, and so on). Receiving operations of a UE may include decoding operations and/or receiving operations of a WAN DL channel and/or a WAN DL signal (e.g., PDCCH, PDSCH, PSS/SSS, and so on). Receiving operations of a UE may include sensing operations and/or CBR measurement operations. In various embodiments of the present disclosure, sensing operations of a UE may include a PSSCH-RSRP measurement operation based on a PSSCH DM-RS sequence, a PSSCH-RSRP measurement operation based on a PSSCH DM-RS sequence, which is scheduled by a PSCCH that is successfully decoded by the UE, a sidelink RSSI (S-RSSI) measurement operation, and/or a S-RSSI measurement operation based on a subchannel related with a V2X resource pool. In various embodiments of the present disclosure, transmitting operations of the UE may include transmitting operations of a sidelink channel and/or sidelink signal (e.g., PSCCH, PSSCH, PSFCH, PSBCH, PSSS/SSSS, and so on). Transmitting operations of the UE may include transmitting operations of a WAN UL channel and/or a WAN UL signal (e.g., PUSCH, PUCCH, SRS, and so on). In various embodiments of the present disclosure, a synchronization signal may include a SLSS and/or PSBCH.

In various embodiments of the present disclosure, configuration may include signaling, signaling from a network, configuration from a network, and/or a pre-configuration from a network. In various embodiments of the present disclosure, definition may include signaling, signaling from a network, configuration from a network, and/or a pre-configuration from a network. In various embodiments of the present disclosure, designation may include signaling, signaling from a network, configuration from a network, and/or a pre-configuration from a network.

In various embodiments of the present disclosure, ProSe Per Packet Priority (PPPP) may be replaced with ProSe Per Packet Reliability (PPPR), and PPPR may be replaced with PPPP. In various embodiments of the present disclosure, as the PPPP value becomes smaller, this may indicate a high priority level, and, as the PPPP value becomes greater, this may indicate a low priority level. In various embodiments of the present disclosure, as the PPPP value becomes smaller, this may indicate a high reliability level, and, as the PPPP value becomes greater, this may indicate a low reliability level. For example, a PPPP value related to a service, packet, or message related to a high priority level may be smaller than a PPPP value related to a service, packet or message related to a low priority level. For example, a PPPR value related to a service, packet or message related to high reliability level may be smaller than a PPPR value related to a service, packet or message related to low reliability level.

In various embodiments of the present disclosure, a session may include at least one of a unicast session (e.g., a unicast session for SL), a groupcast/multicast session (e.g., a groupcast/multicast session for SL), and/or a broadcast session (e.g., a broadcast session for SL).

In various embodiments of the present disclosure, a carrier may be interpreted as at least one of a BWP and/or a resource pool, and vice versa. For example, a carrier may include at least one of a BWP and/or a resource pool. For example, a carrier may include one or more BWPs. For example, a BWP may include one or more resource pools.

FIG. 18 shows a procedure for a UE to determine validity of information related to SL resource(s), in accordance with an embodiment of the present disclosure.

Referring to FIG. 18, in step S1810, a first UE may receive RSC_CINF from RSC_MNG. For example, RSC_MNG may signal RSC_CINF to one or more UEs through a pre-defined channel. For example, RSC_MNG may be at least one of devices (100, 200) other than the first UE, a second UE, a road side unit (RSU), and/or an entity for managing/scheduling SL resource(s). For example, RSC_CINF may be referred to as information related to SL resource(s).

For example, RSC_MNG may limit or restrict resource pool(s) of another UE (e.g., the first UE). For example, RSC_MNG may transmit information for restricting or limiting transmission resource pool(s) and/or reception resource pool(s) of another UE (e.g., the first UE).

For example, RSC_MNG may exclude resource pool(s) of another UE (e.g., the first UE). For example, RSC_MNG may transmit information for excluding transmission resource pool(s) and/or reception resource pool(s) of another UE (e.g., the first UE).

For example, RSC_MNG may schedule resource(s) of another UE (e.g., the first UE). For example, RSC_MNG may transmit information for scheduling transmission resource(s) and/or reception resource(s) of another UE (e.g., the first UE).

For example, RSC_MNG may assist resource selection of another UE (e.g., the first UE). For example, RSC_MNG may transmit assistance information for transmission resource selection and/or reception resource selection of another UE (e.g., the first UE).

For example, RSC_CINF may include information for restricting or limiting resource pool(s) related to SL. For example, RSC_CINF may include information for restricting or limiting resource pool(s) related to SL transmission. For example, RSC_CINF may include information for restricting or limiting resource pool(s) related to SL reception. In this case, for example, a UE receiving the RSC_CINF may select resource(s) for SL communication from within the resource pool(s) related to SL.

For example, RSC_CINF may include information for excluding resource pool(s) related to SL. For example, RSC_CINF may include information for excluding resource pool(s) related to SL transmission. For example, RSC_CINF may include information for excluding resource pool(s) related to SL reception. In this case, for example, a UE receiving the RSC_CINF may select resource(s) for SL communication outside the resource pool(s) related to SL.

For example, RSC_CINF may include information for scheduling resource(s) related to SL. For example, RSC_CINF may include information for scheduling resource(s) related to SL transmission. For example, RSC_CINF may include information for scheduling resource(s) related to SL reception. In this case, for example, a UE receiving the RSC_CINF may perform SL communication using the resource(s) related to SL.

For example, RSC_CINF may include information that assists a UE to select resource(s) related to SL. For example, RSC_CINF may include information that assists the UE to select resource(s) related to SL transmission. For example, RSC_CINF may include information that assists the UE to select resource(s) related to SL reception. In this case, for example, a UE receiving the RSC_CINF may select resource(s) for SL communication by using the RSC_CINF.

Additionally, for example, RSC_CINF may include at least one of target session information and/or identifier information of a target UE (e.g., identifier information of the first UE).

For example, RSC_MNG may periodically transmit RSC_CINF. For example, RSC_MNG may transmit RSC_CINF based on a pre-defined period. For example, RSC_MNG may transmit RSC_CINF based on a timer. For example, if the timer expires, RSC_MNG may transmit RSC_CINF. For example, a value of the pre-defined period and/or a value of the timer may be pre-configured by a network or a base station. For example, RSC_MNG may transmit the value of the pre-defined period and/or the value of the timer to another UE through PC5 RRC signaling. For example, another UE may be a UE that has established a session with RSC_MNG.

For example, RSC_MNG may transmit RSC_CINF to the first UE according to a request of the first UE. For example, the first UE may perform CBR measurement for scheduled resource(s) or restricted resource pool(s) by RSC_CINF previously received from RSC_MNG. In addition, if the measured CBR value is equal to or greater than a pre-configured threshold, the first UE may transmit a request of transmission of RSC_CINF to RSC_MNG. Here, for example, when the first UE requests RSC_MNG to transmit RSC_CINF, the first UE may also transmit the measured CBR information. In this case, RSC_MNG may transmit a new RSC_CINF to the first UE according to the request of transmission of RSC_CINF from the first UE. Alternatively, for example, the first UE may perform occupancy ratio measurement for scheduled resource(s) or restricted resource pool(s) by RSC_CINF previously received from RSC_MNG. In addition, if the measured occupancy ratio value is equal to or greater than a pre-configured threshold, the first UE may transmit a request of transmission of RSC_CINF to RSC_MNG. Here, for example, when the first UE requests RSC_MNG to transmit RSC_CINF, the first UE may also transmit the measured occupancy ratio information. In this case, RSC_MNG may transmit a new RSC_CINF to the first UE according to the request of transmission of RSC_CINF from the first UE. For example, the new RSC_CINF may include at least one of information for scheduling updated SL resource(s) and/or information for restricting updated SL resource(s).

For example, RSC_MNG may perform CBR measurement and/or occupancy ratio measurement for scheduled resource(s) or restricted resource pool(s) to the first UE by the RSC_MNG. In addition, if the measured CBR and/or occupancy ratio value is equal to or greater than a pre-configured threshold, RSC_MNG may transmit a new RSC_CINF to the first UE. For example, the new RSC_CINF may include at least one of information for scheduling updated SL resource(s) and/or information for restricting updated SL resource(s).

In step S1820, the first UE may determine whether or not RSC_CINF is valid. For example, according to at least one rule proposed below, the first UE receiving RSC_CINF from RSC_MNG may determine and/or assume validity of the RSC_CINF.

For example, in case of SL unicast communication, the first UE may determine that the RSC_CINF is valid during time in which a session related to the unicast communication is valid. For example, in case of SL groupcast communication, the first UE may determine that the RSC_CINF is valid during time in which a session related to the groupcast communication is valid. For example, in case of SL broadcast communication, the first UE may determine that the RSC_CINF is valid during time in which a session related to the broadcast communication is valid. For example, the session may be valid until an RLF related to the session is declared. For example, if the RLF related to the session is declared, the session may not be valid. For example, the session may be valid before OUT-OF-SYNCH occurs more than or equal to a pre-configured threshold number. For example, if OUT-OF-SYNCH occurs more than or equal to a pre-configured threshold number, the session may not be valid. For example, the session may be valid before OUT-OF-SYNCH continuously occurs more than or equal to a pre-configured threshold number. For example, if OUT-OF-SYNCH continuously occurs more than or equal to a pre-configured threshold number, the session may not be valid. For example, the session may be valid until SL-related quality less than or equal to a pre-configured threshold is measured/reported. For example, if SL-related quality less than or equal to a pre-configured threshold is measured/reported, the session may not be valid. For example, the session may be valid until SL-related quality less than or equal to a pre-configured threshold is measured/reported continuously. For example, if SL-related quality less than or equal to a pre-configured threshold is measured/reported continuously, the session may not be valid. For example, the SL-related quality may include at least one of SL CSI, RSRP, and/or RSRQ.

Additionally/alternatively, for example, until a pre-configured timer expires, the first terminal UE determine that the RSC_CINF is valid. For example, the timer may be pre-configured from RSC_MNG or a network.

Additionally/alternatively, for example, until strength and/or quality of a signal transmitted by RSC_MNG becomes smaller than a pre-configured threshold, the first UE may determine that the RSC_CINF is valid. For example, until strength and/or quality of a signal received from RSC_MNG becomes smaller than a pre-configured threshold, the first UE may determine that the RSC_CINF is valid. For example, if strength and/or quality of a signal received from RSC_MNG is greater than or equal to a pre-configured threshold, the first UE may determine that the RSC_CINF is valid. For example, strength and/or quality of the signal may include at least one of RSRP and/or RSRQ. For example, the signal may be a reference signal.

Additionally/alternatively, for example, until strength and/or quality of a signal transmitted by RSU becomes smaller than a pre-configured threshold, the first UE may determine that the RSC_CINF is valid. For example, until strength and/or quality of a signal received from RSU becomes smaller than a pre-configured threshold, the first UE may determine that the RSC_CINF is valid. For example, if strength and/or quality of a signal received from RSU is greater than or equal to a pre-configured threshold, the first UE may determine that the RSC_CINF is valid. For example, strength and/or quality of the signal may include at least one of RSRP and/or RSRQ. For example, the signal may be a reference signal.

For example, the timer may be configured differently per a type of SL communication, per a type of SL service, per a priority of SL service, per a ProSe Per Packet Priority (PPPP) related to SL service, and per a ProSe Per Packet Reliability (PPPR) related to SL service, per a delay budget of SL service, and/or per a channel busy ratio (CBR), partially or completely. Additionally/alternatively, for example, the threshold may be configured differently per a type of SL communication, per a type of SL service, per a priority of SL service, per a ProSe Per Packet Priority (PPPP) related to SL service, and per a ProSe Per Packet Reliability (PPPR) related to SL service, per a delay budget of SL service, and/or per a channel busy ratio (CBR), partially or completely. For example, the threshold may be a threshold related to the strength and/or quality of the signal. For example, the type of SL communication may include at least one of unicast communication, groupcast communication, and/or broadcast communication.

Additionally, in step S1830, the first UE may select resource(s) for SL communication. For example, based on whether or not RSC_CINF is valid, the first UE may select resource(s) for SL communication.

For example, if RSC_CINF is valid, the first UE may select resource(s) for SL communication by using information included in RSC_CINF. For example, if RSC_CINF includes information for scheduling SL resource(s), the first UE may select the SL resource(s) and may perform SL communication by using the selected SL resource(s). For example, if RSC_CINF includes information for restricting SL resource pool(s), the first UE may select SL resource(s) within the SL resource pool(s) and may perform SL communication by using the selected SL resource(s). For example, if RSC_CINF includes information for excluding SL resource pool(s), the first UE may select SL resource(s) outside the SL resource pool(s) and may perform SL communication by using the selected SL resource(s).

For example, if RSC_CINF is not valid, the first UE may independently select resource(s) for SL communication. For example, the first UE may select SL resource(s) regardless of information included in RSC_CINF.

According to an embodiment of the present disclosure, there may be no guarantee that the RSC_CINF signaled from the RSC_MNG by the first UE is ideally determined. For example, there may be no guarantee that the information for restricting SL resource pool(s) received by the first UE from the second UE was ideally determined by the second UE. In this case, it is necessary to allow the first UE to use resource(s) other than resource(s) indicated by RSC_CINF. For example, it is necessary for the first UE to perform SL communication by using resource(s) other than the resource(s) indicated by RSC_CINF.

For example, the first UE may receive RSC_CINF including information for scheduling SL resource(s), and the first UE may perform CBR measurement for the SL resource(s). In this case, if the CBR measurement value is greater than or equal to a pre-configured threshold, it is allowed for the first UE to perform SL communication on resource(s) other than the SL resource(s). For example, the first UE may exceptionally perform SL communication on the resource(s) other than the SL resource(s).

Additionally/alternatively, for example, the first UE may receive RSC_CINF including information for scheduling SL resource(s), and the first UE may perform occupancy ratio measurement for the SL resource(s). In this case, if the occupancy ratio is greater than or equal to a pre-configured threshold, it is allowed for the first UE to perform SL communication on resource(s) other than the SL resource(s). For example, the first UE may exceptionally perform SL communication on the resource(s) other than the SL resource(s).

Additionally/alternatively, for example, the first UE may receive RSC_CINF including information for restricting SL resource pool(s), and the first UE may perform CBR measurement for the SL resource pool(s). In this case, if the CBR measurement value is greater than or equal to a pre-configured threshold, it is allowed for the first UE to perform SL communication on resource pool(s) other than the SL resource pool(s). For example, the first UE may exceptionally perform SL communication on the resource pool(s) other than the SL resource pool(s).

Additionally/alternatively, for example, the first UE may receive RSC_CINF including information for restricting SL resource pool(s), and the first UE may perform occupancy ratio measurement for the SL resource pool(s). In this case, if the occupancy ratio is greater than or equal to a pre-configured threshold, it is allowed for the first UE to perform SL communication on resource pool(s) other than the SL resource pool(s). For example, the first UE may exceptionally perform SL communication on the resource pool(s) other than the SL resource pool(s).

For example, in case of at least one of transmission for a message related to a service of a relatively high priority, transmission for a message related to a relatively low PPPR value, transmission for a message related to a relatively low PPPP value, and/or transmission for a message related to a relatively low latency budget value, it is allowed for the first UE to perform SL communication on the resource pool(s) other than the SL resource pool(s) or on the resource(s) other than the SL resource(s). For example, in case of at least one of transmission for a message related to a service of a priority higher than a pre-configured threshold, transmission for a message related to a PPPR value less than a pre-configured threshold, transmission for a message related to a PPPP value less than a pre-configured threshold, and/or transmission for a message related to a latency budget value less than a pre-configured threshold, it is allowed for the first UE to perform SL communication on the resource pool(s) other than the SL resource pool(s) or on the resource(s) other than the SL resource(s). For example, in case of at least one of transmission for a message related to a service of a priority lower than a pre-configured threshold, transmission for a message related to a PPPR value larger than a pre-configured threshold, transmission for a message related to a PPPP value larger than a pre-configured threshold, and/or transmission for a message related to a latency budget value larger than a pre-configured threshold, it is not allowed for the first UE to perform SL communication on the resource pool(s) other than the SL resource pool(s) or on the resource(s) other than the SL resource(s).

According to an embodiment of the present disclosure, a priority order of synchronization sources may be configured differently per a type of SL communication or a type of SL service. For example, the type of SL communication or the type of SL service may include at least one of unicast, groupcast, and broadcast.

For example, in a procedure for performing synchronization, the UE may be configured to prioritize SLSS in unicast, and may be configured to prioritize GNSS in broadcast. For example, the UE may configure SLSS as the highest priority in unicast, and may configure GNSS as the highest priority in broadcast.

Additionally/alternatively, for example, in a procedure for performing synchronization, the UE may be configured to prioritize SLSS in groupcast, and may be configured to prioritize GNSS in broadcast. For example, the UE may configure SLSS as the highest priority in groupcast, and may configure GNSS as the highest priority in broadcast.

Meanwhile, in case the proposed rule is applied on a carrier in which both unicast and/or groupcast and broadcast are configured, if it is necessary for a UE participating in unicast and/or groupcast and broadcast (e.g., receiving UE) to receive all messages related to the unicast and/or groupcast and broadcast, complexity of the UE may increase. For example, the complexity related to synchronization tracking and/or tuning of the UE may increase.

Therefore, for example, according to the type of SL communication or the type of SL service configured for the carrier, which synchronization source is prioritized by the UE may be configured differently. For example, according to the type of SL communication or the type of SL service configured for the carrier, the UE may configure or determine the synchronization source of the highest priority differently.

For example, in case only unicast communication is configured for the carrier, the UE may prioritize SLSS. For example, in case only unicast communication is configured for the carrier, the UE may determine SLSS as the highest priority.

For example, in case only unicast communication and/or groupcast communication is configured for the carrier, the UE may prioritize SLSS. For example, in case only unicast communication and/or groupcast communication is configured for the carrier, the UE may determine SLSS as the highest priority.

For example, in case unicast communication and broadcast communication are configured for the carrier, the UE may prioritize GNSS. For example, in case unicast communication and broadcast communication are configured together on the carrier, the UE may determine GNSS as the highest priority.

For example, in case unicast communication and/or groupcast communication is configured for the carrier together with broadcast communication, the UE may prioritize GNSS. For example, in case unicast communication and/or groupcast communication is configured for the carrier together with broadcast communication, the UE may determine GNSS as the highest priority.

According to various embodiments of the present disclosure, RSC_MNG may efficiently maintain or manage QoS related to SL communication. For example, the UE may select resource(s) for SL communication by using RSC_CINF received from RSC_MNG. Accordingly, in case a plurality of UEs select resource(s) for SL communication based on RSC_CINF, a problem of conflicting selected resource(s) can be alleviated.

According to various embodiments of the present disclosure, the UE can determine/select valid information from among RSC_CINF received from RSC_MNG. For example, if the valid information is used/applied, a problem of conflicting selected resource(s) between UEs can be alleviated. Additionally/alternatively, for example, QoS maintenance/management related to SL communication can be achieved more efficiently. In addition, according to various embodiments of the present disclosure, complexity related to synchronization tracking and/or tuning of the UE can be reduced. For example, on a carrier, the complexity related to synchronization tracking and/or tuning of a receiving UE can be reduced.

FIG. 19 shows a method for determining, by a first device (100), whether or not information related to a sidelink (SL) resource is valid, in accordance with an embodiment of the present disclosure. The embodiment of FIG. 19 may be combined with various embodiments of the present disclosure.

Referring to FIG. 19, in step S1910, the first device (100) may receive the information related to the SL resource from a second device (200).

In step S1920, the first device (100) may determine whether or not the information related to the SL resource is valid, based on power of a signal received from the second device (200).

For example, if the power of the signal received from the second device (200) is greater than or equal to a first threshold, the information related to the SL resource may be determined to be valid. For example, the power of the signal may include at least one of reference signals received power (RSRP) or reference signal received quality (RSRQ) of the signal. For example, the first threshold may be configured based on at least one of a type of SL communication, a priority of a service, a ProSe Per Packet Priority (PPPP) related to the service, a ProSe Per Packet Reliability (PPPR) related to the service, a latency budget of the service, or channel busy ratio (CBR).

For example, the information related to the SL resource may include information for restricting the SL resource of the first device (100).

Additionally, for example, the first device (100) may perform SL communication on the SL resource based on the information related to the SL resource that is available.

Additionally, for example, the first device (100) may measure channel busy ratio (CBR) for the SL resource. In this case, SL communication by the first device (100) on resources other than the SL resource may be allowed based on the measured CBR and a second threshold. For example, if the measured CBR is greater than or equal to the second threshold, the SL communication on resources other than the SL resource may be allowed. For example, the SL communication may include at least one of transmission for a SL service related to a high priority or transmission for a SL service related to a low latency budget.

Additionally, for example, the first device (100) may measure occupancy ratio for the SL resource. In this case, wherein the SL communication by the first device (100) on resources other than the SL resource may be allowed based on the measured occupancy ratio and a third threshold. For example, if the measured occupancy ratio is greater than or equal to the third threshold, the SL communication on resources other than the SL resource may be allowed.

For example, the information related to the SL resource may include information for scheduling the SL resource of the first device (100).

For example, a priority order of a synchronization source may be configured differently per a type of SL communication. For example, the type of the SL communication may include at least one of unicast, groupcast, or broadcast.

The proposed method may be performed by an apparatus according to various embodiments of the present disclosure. First, the processor (102) of the first device (100) may control the transceiver (106) to receive the information related to the SL resource from a second device (200). In addition, the processor (102) of the first device (100) may determine whether or not the information related to the SL resource is valid, based on power of a signal received from the second device (200).

Various embodiments of the present disclosure may be implemented independently. Alternatively, the various embodiments of the present disclosure may be combined or merged with each other. For example, although the various embodiments of the present disclosure have been described based on a 3GPP system for convenience of description, the various embodiments of the present disclosure can extend to other systems apart from the 3GPP system.

Hereinafter, device(s) to which various embodiments of the present disclosure can be applied will be described.

The various descriptions, functions, procedures, proposals, methods, and/or operational flowcharts of the present disclosure described in this document may be applied to, without being limited to, various fields requiring wireless communication/connection (e.g., 5G) between devices.

Hereinafter, a description will be given in more detail with reference to the drawings. In the following drawings/description, the same reference symbols may denote the same or corresponding hardware blocks, software blocks, or functional blocks unless described otherwise.

FIG. 20 shows a communication system (1) in accordance with an embodiment of the present disclosure.

Referring to FIG. 20, a communication system (1) to which various embodiments of the present disclosure are applied includes wireless devices, Base Stations (BSs), and a network. Herein, the wireless devices represent devices performing communication using Radio Access Technology (RAT) (e.g., 5G New RAT (NR)) or Long-Term Evolution (LTE)) and may be referred to as communication/radio/5G devices. The wireless devices may include, without being limited to, a robot (100 a), vehicles (100 b-1, 100 b-2), an eXtended Reality (XR) device (100 c), a hand-held device (100 d), a home appliance (100 e), an Internet of Things (IoT) device (1000, and an Artificial Intelligence (AI) device/server (400). For example, the vehicles may include a vehicle having a wireless communication function, an autonomous vehicle, and a vehicle capable of performing communication between vehicles. Herein, the vehicles may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). The XR device may include an Augmented Reality (AR)/Virtual Reality (VR)/Mixed Reality (MR) device and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smartmeter. For example, the BSs and the network may be implemented as wireless devices and a specific wireless device (200 a) may operate as a BS/network node with respect to other wireless devices.

The wireless devices (100 a-1000 may be connected to the network (300) via the BSs (200). An AI technology may be applied to the wireless devices (100 a-1000 and the wireless devices (100 a-1000 may be connected to the AI server (400) via the network (300). The network (300) may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices (100 a-1000 may communicate with each other through the BSs (200)/network (300), the wireless devices (100 a-1000 may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs/network. For example, the vehicles (100 b-1, 100 b-2) may perform direct communication (e.g., Vehicle-to-Vehicle (V2V)/Vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices (100 a-1000.

Wireless communication/connections (150 a, 150 b, 150 c) may be established between the wireless devices (100 a-1000/BS (200), or BS (200)/BS (200). Herein, the wireless communication/connections may be established through various RATs (e.g., 5G NR) such as uplink/downlink communication (150 a), sidelink communication (150 b) (or, D2D communication), or inter BS communication (e.g. relay, Integrated Access Backhaul (IAB)). The wireless devices and the BSs/the wireless devices may transmit/receive radio signals to/from each other through the wireless communication/connections (150 a, 150 b). For example, the wireless communication/connections (150 a, 150 b) may transmit/receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/demapping), and resource allocating processes, for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure.

FIG. 21 shows wireless devices in accordance with an embodiment of the present disclosure.

Referring to FIG. 21, a first wireless device (100) and a second wireless device (200) may transmit radio signals through various RATs (e.g., LTE and NR). Herein, {the first wireless device (100) and the second wireless device (200)} may correspond to {the wireless device (100 x) and the BS (200)} and/or {the wireless device (100 x) and the wireless device (100 x)} of FIG. 20.

The first wireless device (100) may include one or more processors (102) and one or more memories (104) and additionally further include one or more transceivers (106) and/or one or more antennas (108). The processor(s) (102) may control the memory(s) (104) and/or the transceiver(s) (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s) (102) may process information within the memory(s) (104) to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver(s) (106). The processor(s) (102) may receive radio signals including second information/signals through the transceiver (106) and then store information obtained by processing the second information/signals in the memory(s) (104). The memory(s) (104) may be connected to the processor(s) (102) and may store various information related to operations of the processor(s) (102). For example, the memory(s) (104) may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) (102) or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s) (102) and the memory(s) (104) may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) (106) may be connected to the processor(s) (102) and transmit and/or receive radio signals through one or more antennas (108). Each of the transceiver(s) (106) may include a transmitter and/or a receiver. The transceiver(s) (106) may be interchangeably used with Radio Frequency (RF) unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip.

The second wireless device (200) may include one or more processors (202) and one or more memories (204) and additionally further include one or more transceivers (206) and/or one or more antennas (208). The processor(s) (202) may control the memory(s) (204) and/or the transceiver(s) (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s) (202) may process information within the memory(s) (204) to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver(s) (206). The processor(s) (202) may receive radio signals including fourth information/signals through the transceiver(s) (106) and then store information obtained by processing the fourth information/signals in the memory(s) (204). The memory(s) (204) may be connected to the processor(s) (202) and may store various information related to operations of the processor(s) (202). For example, the memory(s) (204) may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) (202) or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s) (202) and the memory(s) (204) may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) (206) may be connected to the processor(s) (202) and transmit and/or receive radio signals through one or more antennas (208). Each of the transceiver(s) (206) may include a transmitter and/or a receiver. The transceiver(s) (206) may be interchangeably used with RF unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip.

Hereinafter, hardware elements of the wireless devices (100, 200) will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors (102, 202). For example, the one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). The one or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Unit (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors (102, 202) may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document and provide the generated signals to the one or more transceivers (106, 206). The one or more processors (102, 202) may receive the signals (e.g., baseband signals) from the one or more transceivers (106, 206) and obtain the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document.

The one or more processors (102, 202) may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be included in the one or more processors (102, 202) or stored in the one or more memories (104, 204) so as to be driven by the one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software in the form of code, commands, and/or a set of commands.

The one or more memories (104, 204) may be connected to the one or more processors (102, 202) and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. The one or more memories (104, 204) may be configured by Read-Only Memories (ROMs), Random Access Memories (RAMs), Electrically Erasable Programmable Read-Only Memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof. The one or more memories (104, 204) may be located at the interior and/or exterior of the one or more processors (102, 202). The one or more memories (104, 204) may be connected to the one or more processors (102, 202) through various technologies such as wired or wireless connection.

The one or more transceivers (106, 206) may transmit user data, control information, and/or radio signals/channels, mentioned in the methods and/or operational flowcharts of this document, to one or more other devices. The one or more transceivers (106, 206) may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, from one or more other devices. For example, the one or more transceivers (106, 206) may be connected to the one or more processors (102, 202) and transmit and receive radio signals. For example, the one or more processors (102, 202) may perform control so that the one or more transceivers (106, 206) may transmit user data, control information, or radio signals to one or more other devices. The one or more processors (102, 202) may perform control so that the one or more transceivers (106, 206) may receive user data, control information, or radio signals from one or more other devices. The one or more transceivers (106, 206) may be connected to the one or more antennas (108, 208) and the one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, through the one or more antennas (108, 208). In this document, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). The one or more transceivers (106, 206) may convert received radio signals/channels, etc., from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc., using the one or more processors (102, 202). The one or more transceivers (106, 206) may convert the user data, control information, radio signals/channels, etc., processed using the one or more processors (102, 202) from the base band signals into the RF band signals. To this end, the one or more transceivers (106, 206) may include (analog) oscillators and/or filters.

FIG. 22 shows a signal process circuit for a transmission signal in accordance with an embodiment of the present disclosure.

Referring to FIG. 22, a signal processing circuit (1000) may include scramblers (1010), modulators (1020), a layer mapper (1030), a precoder (1040), resource mappers (1050), and signal generators (1060). An operation/function of FIG. 22 may be performed, without being limited to, the processors (102, 202) and/or the transceivers (106, 206) of FIG. 21. Hardware elements of FIG. 22 may be implemented by the processors (102, 202) and/or the transceivers (106, 206) of FIG. 21. For example, blocks 1010˜1060 may be implemented by the processors (102, 202) of FIG. 21. Alternatively, the blocks 1010˜1050 may be implemented by the processors (102, 202) of FIG. 21 and the block 1060 may be implemented by the transceivers (106, 206) of FIG. 21.

Codewords may be converted into radio signals via the signal processing circuit (1000) of FIG. 22. Herein, the codewords are encoded bit sequences of information blocks. The information blocks may include transport blocks (e.g., a UL-SCH transport block, a DL-SCH transport block). The radio signals may be transmitted through various physical channels (e.g., a PUSCH and a PDSCH).

Specifically, the codewords may be converted into scrambled bit sequences by the scramblers (1010). Scramble sequences used for scrambling may be generated based on an initialization value, and the initialization value may include ID information of a wireless device. The scrambled bit sequences may be modulated to modulation symbol sequences by the modulators (1020). A modulation scheme may include pi/2-Binary Phase Shift Keying (pi/2-BP SK), m-Phase Shift Keying (m-PSK), and m-Quadrature Amplitude Modulation (m-QAM). Complex modulation symbol sequences may be mapped to one or more transport layers by the layer mapper (1030). Modulation symbols of each transport layer may be mapped (precoded) to corresponding antenna port(s) by the precoder (1040). Outputs z of the precoder (1040) may be obtained by multiplying outputs y of the layer mapper (1030) by an N*M precoding matrix W. Herein, N is the number of antenna ports and M is the number of transport layers. The precoder (1040) may perform precoding after performing transform precoding (e.g., DFT) for complex modulation symbols. Alternatively, the precoder (1040) may perform precoding without performing transform precoding.

The resource mappers (1050) may map modulation symbols of each antenna port to time-frequency resources. The time-frequency resources may include a plurality of symbols (e.g., a CP-OFDMA symbols and DFT-s-OFDMA symbols) in the time domain and a plurality of subcarriers in the frequency domain. The signal generators (1060) may generate radio signals from the mapped modulation symbols and the generated radio signals may be transmitted to other devices through each antenna. For this purpose, the signal generators (1060) may include Inverse Fast Fourier Transform (IFFT) modules, Cyclic Prefix (CP) inserters, Digital-to-Analog Converters (DACs), and frequency up-converters.

Signal processing procedures for a signal received in the wireless device may be configured in a reverse manner of the signal processing procedures (1010˜1060) of FIG. 22. For example, the wireless devices (e.g., 100, 200 of FIG. 21) may receive radio signals from the exterior through the antenna ports/transceivers. The received radio signals may be converted into baseband signals through signal restorers. To this end, the signal restorers may include frequency downlink converters, Analog-to-Digital Converters (ADCs), CP remover, and Fast Fourier Transform (FFT) modules. Next, the baseband signals may be restored to codewords through a resource demapping procedure, a postcoding procedure, a demodulation processor, and a descrambling procedure. The codewords may be restored to original information blocks through decoding. Therefore, a signal processing circuit (not illustrated) for a reception signal may include signal restorers, resource demappers, a postcoder, demodulators, descramblers, and decoders.

FIG. 23 shows another example of a wireless device in accordance with an embodiment of the present disclosure. The wireless device may be implemented in various forms according to a use-case/service (refer to FIG. 20).

Referring to FIG. 23, wireless devices (100, 200) may correspond to the wireless devices (100, 200) of FIG. 21 and may be configured by various elements, components, units/portions, and/or modules. For example, each of the wireless devices (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional components (140). The communication unit may include a communication circuit (112) and transceiver(s) (114). For example, the communication circuit (112) may include the one or more processors (102, 202) and/or the one or more memories (104, 204) of FIG. 21. For example, the transceiver(s) (114) may include the one or more transceivers (106, 206) and/or the one or more antennas (108, 208) of FIG. 21. The control unit (120) is electrically connected to the communication unit (110), the memory (130), and the additional components (140) and controls overall operation of the wireless devices. For example, the control unit (120) may control an electric/mechanical operation of the wireless device based on programs/code/commands/information stored in the memory unit (130). The control unit (120) may transmit the information stored in the memory unit (130) to the exterior (e.g., other communication devices) via the communication unit (110) through a wireless/wired interface or store, in the memory unit (130), information received through the wireless/wired interface from the exterior (e.g., other communication devices) via the communication unit (110).

The additional components (140) may be variously configured according to types of wireless devices. For example, the additional components (140) may include at least one of a power unit/battery, input/output (I/O) unit, a driving unit, and a computing unit. The wireless device may be implemented in the form of, without being limited to, the robot (100 a of FIG. 20), the vehicles (100 b-1 and 100 b-2 of FIG. 20), the XR device (100 c of FIG. 20), the hand-held device (100 d of FIG. 20), the home appliance (100 e of FIG. 20), the IoT device (100 f of FIG. 20), a digital broadcast terminal, a hologram device, a public safety device, an MTC device, a medicine device, a fintech device (or a finance device), a security device, a climate/environment device, the AI server/device (400 of FIG. 20), the BSs (200 of FIG. 20), a network node, etc. The wireless device may be used in a mobile or fixed place according to a use-example/service.

In FIG. 23, the entirety of the various elements, components, units/portions, and/or modules in the wireless devices (100, 200) may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit (110). For example, in each of the wireless devices (100, 200), the control unit (120) and the communication unit (110) may be connected by wire and the control unit (120) and first units (e.g., 130, 140) may be wirelessly connected through the communication unit (110). Each element, component, unit/portion, and/or module within the wireless devices (100, 200) may further include one or more elements. For example, the control unit (120) may be configured by a set of one or more processors. As an example, the control unit (120) may be configured by a set of a communication control processor, an application processor, an Electronic Control Unit (ECU), a graphical processing unit, and a memory control processor. As another example, the memory (130) may be configured by a Random Access Memory (RAM), a Dynamic RAM (DRAM), a Read Only Memory (ROM)), a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof.

Hereinafter, an example of implementing FIG. 23 will be described in detail with reference to the drawings.

FIG. 24 shows a hand-held device in accordance with an embodiment of the present disclosure. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), or a portable computer (e.g., a notebook). The hand-held device may be referred to as a mobile station (MS), a user terminal (UT), a Mobile Subscriber Station (MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), or a Wireless Terminal (WT).

Referring to FIG. 24, a hand-held device (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a memory unit (130), a power supply unit (140 a), an interface unit (140 b), and an I/O unit (140 c). The antenna unit (108) may be configured as a part of the communication unit (110). Blocks 110˜130/140 a˜140 c correspond to the blocks 110˜130/140 of FIG. 23, respectively.

The communication unit (110) may transmit and receive signals (e.g., data and control signals) to and from other wireless devices or BSs. The control unit (120) may perform various operations by controlling constituent elements of the hand-held device (100). The control unit (120) may include an Application Processor (AP). The memory unit (130) may store data/parameters/programs/code/commands needed to drive the hand-held device (100). The memory unit (130) may store input/output data/information. The power supply unit (140 a) may supply power to the hand-held device (100) and include a wired/wireless charging circuit, a battery, etc. The interface unit (140 b) may support connection of the hand-held device (100) to other external devices. The interface unit (140 b) may include various ports (e.g., an audio I/O port and a video I/O port) for connection with external devices. The I/O unit (140 c) may input or output video information/signals, audio information/signals, data, and/or information input by a user. The I/O unit (140 c) may include a camera, a microphone, a user input unit, a display unit (140 d), a speaker, and/or a haptic module.

As an example, in the case of data communication, the I/O unit (140 c) may obtain information/signals (e.g., touch, text, voice, images, or video) input by a user and the obtaind information/signals may be stored in the memory unit (130). The communication unit (110) may convert the information/signals stored in the memory into radio signals and transmit the converted radio signals to other wireless devices directly or to a BS. The communication unit (110) may receive radio signals from other wireless devices or the BS and then restore the received radio signals into original information/signals. The restored information/signals may be stored in the memory unit (130) and may be output as various types (e.g., text, voice, images, video, or haptic) through the I/O unit (140 c).

FIG. 25 shows a vehicle or an autonomous vehicle in accordance with an embodiment of the present disclosure. The vehicle or autonomous vehicle may be implemented by a mobile robot, a car, a train, a manned/unmanned Aerial Vehicle (AV), a ship, etc.

Referring to FIG. 25, a vehicle or autonomous vehicle (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a driving unit (140 a), a power supply unit (140 b), a sensor unit (140 c), and an autonomous driving unit (140 d). The antenna unit (108) may be configured as a part of the communication unit (110). The blocks 110/130/140 a-140 d correspond to the blocks 110/130/140 of FIG. 23, respectively.

The communication unit (110) may transmit and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and road side units), and servers. The control unit (120) may perform various operations by controlling elements of the vehicle or the autonomous vehicle (100). The control unit (120) may include an Electronic Control Unit (ECU). The driving unit (140 a) may cause the vehicle or the autonomous vehicle (100) to drive on a road. The driving unit (140 a) may include an engine, a motor, a powertrain, a wheel, a brake, a steering device, etc. The power supply unit (140 b) may supply power to the vehicle or the autonomous vehicle (100) and include a wired/wireless charging circuit, a battery, etc. The sensor unit (140 c) may obtain a vehicle state, ambient environment information, user information, etc. The sensor unit (140 c) may include an Inertial Measurement Unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a position module, a vehicle forward/backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illumination sensor, a pedal position sensor, etc. The autonomous driving unit (140 d) may implement technology for maintaining a lane on which a vehicle is driving, technology for automatically adjusting speed, such as adaptive cruise control, technology for autonomously driving along a determined path, technology for driving by automatically setting a path if a destination is set, and the like.

For example, the communication unit (110) may receive map data, traffic information data, etc., from an external server. The autonomous driving unit (140 d) may generate an autonomous driving path and a driving plan from the obtained data. The control unit (120) may control the driving unit (140 a) such that the vehicle or the autonomous vehicle (100) may move along the autonomous driving path according to the driving plan (e.g., speed/direction control). In the middle of autonomous driving, the communication unit (110) may aperiodically/periodically obtain recent traffic information data from the external server and obtain surrounding traffic information data from neighboring vehicles. In the middle of autonomous driving, the sensor unit (140 c) may obtain a vehicle state and/or surrounding environment information. The autonomous driving unit (140 d) may update the autonomous driving path and the driving plan based on the newly obtained data/information. The communication unit (110) may transfer information on a vehicle position, the autonomous driving path, and/or the driving plan to the external server. The external server may predict traffic information data using AI technology, etc., based on the information collected from vehicles or autonomous vehicles and provide the predicted traffic information data to the vehicles or the autonomous vehicles.

FIG. 26 shows a vehicle in accordance with an embodiment of the present disclosure. The vehicle may be implemented as a transport means, an aerial vehicle, a ship, etc.

Referring to FIG. 26, a vehicle (100) may include a communication unit (110), a control unit (120), a memory unit (130), an I/O unit (140 a), and a positioning unit (140 b). Herein, the blocks 110˜130/140 a˜140 b correspond to blocks 110˜130/140 of FIG. 23.

The communication unit (110) may transmit and receive signals (e.g., data and control signals) to and from external devices such as other vehicles or BSs. The control unit (120) may perform various operations by controlling constituent elements of the vehicle (100). The memory unit (130) may store data/parameters/programs/code/commands for supporting various functions of the vehicle (100). The I/O unit (140 a) may output an AR/VR object based on information within the memory unit (130). The I/O unit (140 a) may include an HUD. The positioning unit (140 b) may obtain information on the position of the vehicle (100). The position information may include information on an absolute position of the vehicle (100), information on the position of the vehicle (100) within a traveling lane, acceleration information, and information on the position of the vehicle (100) from a neighboring vehicle. The positioning unit (140 b) may include a GPS and various sensors.

As an example, the communication unit (110) of the vehicle (100) may receive map information and traffic information from an external server and store the received information in the memory unit (130). The positioning unit (140 b) may obtain the vehicle position information through the GPS and various sensors and store the obtained information in the memory unit (130). The control unit (120) may generate a virtual object based on the map information, traffic information, and vehicle position information and the I/O unit (140 a) may display the generated virtual object in a window in the vehicle (1410, 1420). The control unit (120) may determine whether the vehicle (100) normally drives within a traveling lane, based on the vehicle position information. If the vehicle (100) abnormally exits from the traveling lane, the control unit (120) may display a warning on the window in the vehicle through the I/O unit (140 a). In addition, the control unit (120) may broadcast a warning message regarding driving abnormity to neighboring vehicles through the communication unit (110). According to situation, the control unit (120) may transmit the vehicle position information and the information on driving/vehicle abnormality to related organizations.

FIG. 27 shows an XR device in accordance with an embodiment of the present disclosure. The XR device may be implemented by an HMD, an HUD mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, etc.

Referring to FIG. 27, an XR device (100 a) may include a communication unit (110), a control unit (120), a memory unit (130), an I/O unit (140 a), a sensor unit (140 b), and a power supply unit (140 c). Herein, the blocks 110˜130/140 a˜140 c correspond to the blocks 110˜130/140 of FIG. 23, respectively.

The communication unit (110) may transmit and receive signals (e.g., media data and control signals) to and from external devices such as other wireless devices, hand-held devices, or media servers. The media data may include video, images, and sound. The control unit (120) may perform various operations by controlling constituent elements of the XR device (100 a). For example, the control unit (120) may be configured to control and/or perform procedures such as video/image acquisition, (video/image) encoding, and metadata generation and processing. The memory unit (130) may store data/parameters/programs/code/commands needed to drive the XR device (100 a)/generate XR object. The I/O unit (140 a) may obtain control information and data from the exterior and output the generated XR object. The I/O unit (140 a) may include a camera, a microphone, a user input unit, a display unit, a speaker, and/or a haptic module. The sensor unit (140 b) may obtain an XR device state, surrounding environment information, user information, etc. The sensor unit (140 b) may include a proximity sensor, an illumination sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, a light sensor, a microphone and/or a radar. The power supply unit (140 c) may supply power to the XR device (100 a) and include a wired/wireless charging circuit, a battery, etc.

For example, the memory unit (130) of the XR device (100 a) may include information (e.g., data) needed to generate the XR object (e.g., an AR/VR/MR object). The I/O unit (140 a) may receive a command for manipulating the XR device (100 a) from a user and the control unit (120) may drive the XR device (100 a) according to a driving command of a user. For example, when a user desires to watch a film or news through the XR device (100 a), the control unit (120) transmits content request information to another device (e.g., a hand-held device (100 b)) or a media server through the communication unit (130). The communication unit (130) may download/stream content such as films or news from another device (e.g., the hand-held device (100 b)) or the media server to the memory unit (130). The control unit (120) may control and/or perform procedures such as video/image acquisition, (video/image) encoding, and metadata generation/processing with respect to the content and generate/output the XR object based on information on a surrounding space or a real object obtained through the I/O unit (140 a)/sensor unit (140 b).

The XR device (100 a) may be wirelessly connected to the hand-held device (100 b) through the communication unit (110) and the operation of the XR device (100 a) may be controlled by the hand-held device (100 b). For example, the hand-held device (100 b) may operate as a controller of the XR device (100 a). To this end, the XR device (100 a) may obtain information on a 3D position of the hand-held device (100 b) and generate and output an XR object corresponding to the hand-held device (100 b).

FIG. 28 shows a robot in accordance with an embodiment of the present disclosure. The robot may be categorized into an industrial robot, a medical robot, a household robot, a military robot, etc., according to a used purpose or field.

Referring to FIG. 28, a robot (100) may include a communication unit (110), a control unit (120), a memory unit (130), an I/O unit (140 a), a sensor unit (140 b), and a driving unit (140 c). Herein, the blocks 110˜130/140 a˜140 c correspond to the blocks 110˜130/140 of FIG. 23, respectively.

The communication unit (110) may transmit and receive signals (e.g., driving information and control signals) to and from external devices such as other wireless devices, other robots, or control servers. The control unit (120) may perform various operations by controlling constituent elements of the robot (100). The memory unit (130) may store data/parameters/programs/code/commands for supporting various functions of the robot (100). The I/O unit (140 a) may obtain information from the exterior of the robot (100) and output information to the exterior of the robot (100). The I/O unit (140 a) may include a camera, a microphone, a user input unit, a display unit, a speaker, and/or a haptic module. The sensor unit (140 b) may obtain internal information of the robot (100), surrounding environment information, user information, etc. The sensor unit (140 b) may include a proximity sensor, an illumination sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertial sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, a light sensor, a microphone, a radar, etc. The driving unit (140 c) may perform various physical operations such as movement of robot joints. In addition, the driving unit (140 c) may cause the robot (100) to travel on the road or to fly. The driving unit (140 c) may include an actuator, a motor, a wheel, a brake, a propeller, etc.

FIG. 29 shows an AI device in accordance with an embodiment of the present disclosure. The AI device may be implemented by a fixed device or a mobile device, such as a TV, a projector, a smartphone, a PC, a notebook, a digital broadcast terminal, a tablet PC, a wearable device, a Set Top Box (STB), a radio, a washing machine, a refrigerator, a digital signage, a robot, a vehicle, etc.

Referring to FIG. 29, an AI device (100) may include a communication unit (110), a control unit (120), a memory unit (130), an I/O unit (140 a/140 b), a learning processor unit (140 c), and a sensor unit (140 d). The blocks 110˜130/140 a˜140 d correspond to blocks 110˜130/140 of FIG. 23, respectively.

The communication unit (110) may transmit and receive wired/radio signals (e.g., sensor information, user input, learning models, or control signals) to and from external devices such as other AI devices (e.g., 100 x, 200, or 400 of FIG. 20) or an AI server (e.g., 400 of FIG. 20) using wired/wireless communication technology. To this end, the communication unit (110) may transmit information within the memory unit (130) to an external device and transmit a signal received from the external device to the memory unit (130).

The control unit (120) may determine at least one feasible operation of the AI device (100), based on information which is determined or generated using a data analysis algorithm or a machine learning algorithm. The control unit (120) may perform an operation determined by controlling constituent elements of the AI device (100). For example, the control unit (120) may request, search, receive, or use data of the learning processor unit (140 c) or the memory unit (130) and control the constituent elements of the AI device (100) to perform a predicted operation or an operation determined to be preferred among at least one feasible operation. The control unit (120) may collect history information including the operation contents of the AI device (100) and operation feedback by a user and store the collected information in the memory unit (130) or the learning processor unit (140 c) or transmit the collected information to an external device such as an AI server (400 of FIG. 20). The collected history information may be used to update a learning model.

The memory unit (130) may store data for supporting various functions of the AI device (100). For example, the memory unit (130) may store data obtained from the input unit (140 a), data obtained from the communication unit (110), output data of the learning processor unit (140 c), and data obtained from the sensor unit (140). The memory unit (130) may store control information and/or software code needed to operate/drive the control unit (120).

The input unit (140 a) may obtain various types of data from the exterior of the AI device (100). For example, the input unit (140 a) may obtain learning data for model learning, and input data to which the learning model is to be applied. The input unit (140 a) may include a camera, a microphone, and/or a user input unit. The output unit (140 b) may generate output related to a visual, auditory, or tactile sense. The output unit (140 b) may include a display unit, a speaker, and/or a haptic module. The sensing unit (140) may obtain at least one of internal information of the AI device (100), surrounding environment information of the AI device (100), and user information, using various sensors. The sensor unit (140) may include a proximity sensor, an illumination sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, a light sensor, a microphone, and/or a radar.

The learning processor unit (140 c) may learn a model consisting of artificial neural networks, using learning data. The learning processor unit (140 c) may perform AI processing together with the learning processor unit of the AI server (400 of FIG. 20). The learning processor unit (140 c) may process information received from an external device through the communication unit (110) and/or information stored in the memory unit (130). In addition, an output value of the learning processor unit (140 c) may be transmitted to the external device through the communication unit (110) and may be stored in the memory unit (130).

Claims in the present description can be combined in various ways. For instance, technical features in method claims of the present description can be combined to be implemented or performed in an apparatus, and technical features in apparatus claims can be combined to be implemented or performed in a method. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in an apparatus. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in a method. 

What is claimed is:
 1. A method for determining, by a first device (100), whether or not information related to a sidelink (SL) resource is valid, the method comprising: receiving the information related to the SL resource from a second device (200); and determining whether or not the information related to the SL resource is valid, based on power of a signal received from the second device (200).
 2. The method of claim 1, wherein, if the power of the signal received from the second device (200) is greater than or equal to a first threshold, the information related to the SL resource is determined to be valid.
 3. The method of claim 2, wherein the power of the signal includes at least one of reference signals received power (RSRP) or reference signal received quality (RSRQ) of the signal.
 4. The method of claim 2, wherein the first threshold is configured based on at least one of a type of SL communication, a priority of a service, a ProSe Per Packet Priority (PPPP) related to the service, a ProSe Per Packet Reliability (PPPR) related to the service, a latency budget of the service, or channel busy ratio (CBR).
 5. The method of claim 1, wherein the information related to the SL resource includes information for restricting the SL resource of the first device (100).
 6. The method of claim 5, further comprising: performing SL communication on the SL resource based on the information related to the SL resource that is available.
 7. The method of claim 5, further comprising: measuring channel busy ratio (CBR) for the SL resource, wherein SL communication by the first device (100) on resources other than the SL resource is allowed based on the measured CBR and a second threshold.
 8. The method of claim 7, wherein, if the measured CBR is greater than or equal to the second threshold, the SL communication on resources other than the SL resource is allowed.
 9. The method of claim 7, wherein the SL communication includes at least one of transmission for a SL service related to a high priority or transmission for a SL service related to a low latency budget.
 10. The method of claim 5, further comprising: measuring occupancy ratio for the SL resource, wherein the SL communication by the first device (100) on resources other than the SL resource is allowed based on the measured occupancy ratio and a third threshold.
 11. The method of claim 10, wherein, if the measured occupancy ratio is greater than or equal to the third threshold, the SL communication on resources other than the SL resource is allowed.
 12. The method of claim 1, wherein the information related to the SL resource includes information for scheduling the SL resource of the first device (100).
 13. The method of claim 1, wherein a priority order of a synchronization source is configured differently per a type of SL communication.
 14. The method of claim 13, wherein the type of the SL communication includes at least one of unicast, groupcast, or broadcast.
 15. A first device (100) determining whether or not information related to a sidelink (SL) resource is valid, the first device (100) comprising: one or more memories; one or more transceivers; and one or more processors connected to the one or more memories and the one or more transceivers, wherein the one or more processors are configured to: receive the information related to the SL resource from a second device (200); and determine whether or not the information related to the SL resource is valid, based on power of a signal received from the second device (200). 